Confirm usage-limit resets before redemption - #33845
Merged
copyberry[bot] merged 1 commit intoJul 17, 2026
Merged
Conversation
## Why Selecting a usage-limit reset from the picker immediately started redemption, leaving no opportunity to verify the choice. ## What changed - Open a separate confirmation popup before redeeming a selected reset, with `No, go back` selected by default. - Show backend-provided reset titles and descriptions in the picker and confirmation, with generic fallback copy when those details are absent. - Ignore duplicate or stale confirmation and redemption events, while retaining the idempotency key needed to retry a failed redemption. ## Testing - Added coverage for confirmation, cancellation, backend copy, duplicate and stale events, successful redemption, and retry behavior. GitOrigin-RevId: 828945f99f06e8c73941fd864e4aa9ac52729f98
copyberry
Bot
force-pushed
the
copyberry/codex-internal-to-codex-oss/828945f99f06e8c73941fd864e4aa9ac52729f98
branch
from
July 17, 2026 15:29
70279a5 to
a50e822
Compare
copyberry
Bot
deleted the
copyberry/codex-internal-to-codex-oss/828945f99f06e8c73941fd864e4aa9ac52729f98
branch
July 17, 2026 15:30
futaowei-web
temporarily deployed
to
issue-triage
July 17, 2026 15:34 — with 
GitHub Actions
Inactive
futaowei-web
temporarily deployed
to
issue-triage
July 17, 2026 15:34 — with
GitHub Actions
Inactive
futaowei-web
temporarily deployed
to
issue-triage
July 17, 2026 15:34 — with
GitHub Actions
Inactive
yizhoupan3-debug
temporarily deployed
to
issue-triage
July 17, 2026 15:34 — with
GitHub Actions
Inactive
yizhoupan3-debug
temporarily deployed
to
issue-triage
July 17, 2026 15:34 — with
GitHub Actions
Inactive
yizhoupan3-debug
temporarily deployed
to
issue-triage
July 17, 2026 15:34 — with
GitHub Actions
Inactive
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Confirm usage-limit resets before redemption
Why
Selecting a usage-limit reset from the picker immediately started redemption,
leaving no opportunity to verify the choice.
What changed
No, go backselected by default.confirmation, with generic fallback copy when those details are absent.
the idempotency key needed to retry a failed redemption.
Testing
stale events, successful redemption, and retry behavior.